fix: Ignore email and phone assertions when token hash is being verified #1
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
https://supabase.com/docs/guides/auth/auth-email-passwordless?queryGroups=language&language=dart#with-magic-link
Following the above link, verifying token hash from magic link doesn't require email or phone in request body (only token hash and type is required in the js example) (It also throws error if email is passed in request body).
Previous state of the code threw assertion error if neither email nor phone is present in verifyOtp call preventing users to verify token hash without passing email or phone in request body.
Hence have added a condition that will ignore the first email and phone assertion if token hash is populated